• 专利附录
  • 专利说明
  • 权利要求
  • 类似技术
  • 同族专利
  • 引用文献
  • 法律状态
  • 优先权
    • 专利摘要:
    method and device for relay node. relay node (110) to a radio access network (100), arranged to be a relay node between one or more user equipment (105) in a cell (125) of the radio access network and the station. base (115) serving the cell. the relay node (110) is arranged to identify itself as the transmit node in the cell (125) in the radio access network (100) and is arranged to receive an indication of no support, indicating that the base station serving the cell (125) is unable to support the relay node. the relay node (110) is arranged to, upon receiving the aforementioned unsupported indication, try to establish itself as a relay node in another cell.
    公开号:BR112012032065B1
    申请号:R112012032065-3
    申请日:2010-06-22
    公开日:2021-07-27
    发明作者:Fredrik Gunnarsson；Stefan Engström；Gunnar Mildh；Walter Muller；Robert Petersen
    申请人:Telefonaktiebolaget Lm Ericsson；
    IPC主号:
    专利说明:

    TECHNICAL FIELD
    [001] The present invention discloses a relay node for a radio access network, as well as a network node and a method for operating a relay node in a radio access network. FUNDAMENTALS
    [002] An important aspect of wireless networks, in this case mobile phone networks, is to ensure that the use of the network is simple and that its operating costs are efficient. Preferably, the network should also be self-organizing in as many aspects as possible. Another aspect that is important is to ensure that the network has good coverage. One way to improve the coverage of a mobile telephone system is to use relay nodes, which serve as "intermediate stations" between the mobile terminals in a system cell and the base station serving the cell. Usually, the same technology is used, both for the user data between a mobile terminal and a relay node, and for the connection between the relay node and the base station.
    [003] A problem with the use of relay nodes in a mobile phone network is that not all base stations in the network may be able to support relay nodes.
    [004] A relay node support for broadcasting from all base stations was proposed to solve this problem, but a difficulty with this solution is that it comprises quite expensive signaling, which would be needed only when the relay nodes are installed and powered for the first time. SUMMARY
    [005] An objective of the present invention is to provide an improved solution to the problem of base stations that are not capable of supporting relay nodes.
    [006] This purpose is served by the present invention in that it discloses a relay node, for a radio access network, which is arranged to be the relay node between one or more User Equipment in a network cell access radio and the base station serving the cell.
    [007] The relay node is arranged to identify itself as a relay node in the cell in the radio access network, and is also arranged to receive a non-support indication, indicating that the base station serving the cell is unable to support the relay node. Furthermore, the relay node is arranged to, upon receiving the aforementioned indication of no support, try to establish itself as a relay node in another cell.
    [008] In one embodiment, the relay node is arranged to identify itself as a relay node in a cell by transmitting one or more connect messages as part of an initial connect procedure.
    [009] In one embodiment, the relay node is arranged to transmit the one or more messages to a separate configuration node in a radio access network or in a core network to which the radio access network is connected, and to receive the unsupported indication and additional information from the configuration node.
    [0010] In one embodiment, the relay node is arranged to interpret the absence of response to one or more connection messages as an indication of unsupported.
    [0011] In one embodiment, the relay node is arranged to transmit the one or more connection messages as one or more of: - A dedicated Radio Resource Control message, - A dedicated cause of establishment in a Request Message RRC Connection Setup, - A dedicated indication in a complete RRC Connection Preparation message; - A random access preamble, where information about the random access preamble suitable for use in the cell is transmitted by the base station serving the cell.
    [0012] In one embodiment, the relay node is arranged to receive, along with the non-support indication, additional information comprising one or more of: - an indication of why the base station serving the cell is unable to support relay nodes; - an alternative carrier or frequency band, intended for relay node communication; - an alternative Radio Access technology, RAT, intended for relay node communication; - a list of one or more cells supported by relay nodes; - a list of one or more cells where relay nodes are not supported. In this mode, the relay node is arranged to use the additional information when trying to establish itself as a relay node in another cell.
    [0013] The notion of "a cell in which the relay node is supported" is used here in the sense that the eNodeB serving the cell supports relay nodes. A special case arises when the cell in which the relay node tries to establish itself is already served by a relay node, so the relay node tries to connect with another relay node. In this case, the cell will not support relay nodes unless the relay node serving the cell supports relay nodes, that is, the relay node in service supports a "multi-hop" relay.
    [0014] In one embodiment, the relay node is arranged to receive the list of one or more cells that support relay nodes, and/or the list of one or more cells that do not support relay nodes, in the form of one or more ranges of cell identifiers.
    [0015] The invention also discloses a network node for a Radio Access Network or a Core Network, arranged to interact with a relay node of the invention, as well as a method for operating the relay node. The network node, the method and the relay node will be described in more detail in the detailed description made in this text. BRIEF DESCRIPTION OF THE DRAWINGS
    [0016] The invention will be described in more detail in the text below, with reference to the attached drawings, in which:
    [0017] Fig. 1 shows a schematic view of the use of the relay node of the present invention, and
    [0018] Fig. 2 shows a schematic block diagram of the relay node of the invention, and
    [0019] Fig. 3 shows the diagram of a signaling of a modality, and
    [0020] Fig. 4 shows a schematic block diagram of a network node of the invention, and
    [0021] Figs. 5 to 7 show different modalities of how the relay node of the invention interfaces with other nodes, and
    [0022] Fig. 8 shows a schematic flowchart of a method of the invention. DETAILED DESCRIPTION
    [0023] Fig. 1 shows a schematic overview of a system 100 in which the invention is used. The system 100, as well as the invention as such, will be described in the text below using LTE system terminology, Long Term Evolution. It should be noted that this is merely by way of example, to facilitate the reader's understanding of the invention, and should not be used to restrict the scope of protection sought by, or granted to the invention, which may also be used in other types of systems such as, for example, WCDMA and GSM systems.
    [0024] The system 100 comprises one or more cells 125, each of which is served by a base station 115, which in an LTE system is known as eNodeB. Each eNodeB can serve one or more cells, such as 125, and is connected to a core network, in this example the so-called Evolved Packet Core 130, EPC, through a plurality of intermediate nodes that are not shown in Fig. 1.
    [0025] In each cell 125 there may be a plurality of User Equipment 105, to increase the coverage of cell 125, the cell has been provided with a relay node 110 that connects one or more of the User Equipment, UEs, with the eNodeB 115. Suitably, the same connection type is used between the UEs and the relay node, as well as between the relay node and the eNodeB.
    [0026] To support relay nodes, base stations need dedicated functionality. For the eNodeB in an LTE system, this functionality includes: • an S1 and X2 proxy functionality, which means that S1 and X2 connections to/from the relay node and forward are terminated and forwarded to the eNodeB serving the relay node , • an S11 termination, which means that secure tunnels can be established between the eNodeBs and other nodes; • a server Gateway (S-GW) functionality, which is responsible for the user plan to handle connections served by the relay, rather than an S-GW in the core network, • a dedicated physical layer and MAC layer signaling and procedures, depending on whether the relay node backhaul is in-band or out-of-band. In-band here is used to denote the case where the connection between the eNodeB and the relay node uses the same frequency band as the connection between the eNodeB and the UEs in the cell, and out-of-band is used here to denote the in which case the connection between the eNode B and the relay node uses another frequency band than the connection between the eNodeB and the UEs in the cell.
    [0027] As mentioned before, all eNodeBs and relay nodes in an LTE system may not be able to handle the function of a relay node, for example, due to the fact that some eNodeBs may be older, and this form not provided with the necessary functionality. Due to this fact, the relay node that tries to establish itself as a relay node in a cell may not be able to do so successfully if the cell is served by an eNodeB that does not support the function of a relay node.
    [0028] Through the present invention, a relay node that fails to establish itself in a cell will be notified that the failure is due to the fact that the eNodeB does not support relay nodes, which means that the relay node it can avoid further unnecessary attempts to establish itself in that particular cell, and may instead try to establish itself as a relay node in another cell.
    [0029] Before making a description of the functionality of the relay node 110 of the invention, in its various embodiments, a brief description of some of the most important components of the relay node 100 will be made with reference to Fig. 2 which shows schematically a block diagram of a relay node 110.
    [0030] As shown in Fig.2, the relay node 110 comprises a receiving unit Rx 215 and a transmitting unit TX 220. The transmitting unit 220 and the receiving unit 215 are connected with an antenna interface 210 which the connects with an antenna unit 205, whereby they transmit to/receive transmissions from the UEs in cell 125 and the eNodeB 115.
    [0031] The relay node 110 also comprises a control unit 225 for controlling the function of the relay node, including the functions of the transmit and receive units 220, 215. In addition, the relay node 110 also comprises a relay unit memory 230 connected to the control unit, for storing data for the operation of the relay node 110.
    [0032] The relay node 110 is arranged to identify itself as the relay node in cell 125 in radio access network 100, and is also arranged to receive a non-support indication indicating that the eNodeB 115 is serving to cell 125 is unable to support a relay node. Examples of the unsupported indication will be described in more detail later in this text, but as its name implies, it is an indication that allows the relay node 100 to understand that the eNodeB 115 is unable to support a relay node. Along with the unsupported indication, the relay node 110 is also, in one embodiment, arranged to receive additional information comprising one or more of the following: • an indication of why the base station 115 serving the cell 125 is unable to support relay nodes, • an alternate carrier or frequency band intended for relay node communication, • and/or a list of one or more cells in which the relay nodes are not supported (white list) , and • a list of one or more cells where relay nodes are not supported.
    [0033] This is illustrated schematically in Fig. 3, which shows a relay node transmitting a relay node indication to a network node, such as, for example, an eNodeB or a Mobility Management Entity, MME, and receiving in response an indication of no support and additional information.
    [0034] The indication of why base station 115 serving cell 125 is unable to support relay nodes may comprise the following reasons: • lack of software support - eNodeB software is not configured to handle relay nodes relay, or software version does not support handling relay nodes, • no S-GW functionality, • no X2 and S1 proxy functionality, • no S11 functionality, • relay node, no multi support -hop" - eNodeB is in fact a relay node itself, and thus is unable to support other relay nodes, • insufficient resources to support another relay node, typically because eNodeB already handles the number of nodes of relay it is capable of.
    [0035] In one embodiment, relay node 110 is arranged to identify itself as a relay node in cell 125 by transmitting one or more connect messages as part of the initial connect procedure.
    [0036] In one embodiment, relay node 110 performs the attach procedure as if it were a UE in cell 125. Part of this procedure involves signaling a NAS message to core network 120, along with information about the UE in annexation. From this information, the core network will be able to disclose that the UE being attached is actually a relay node, and can inform the eNodeB 115 of this, i.e., that there is relay node in cell 125 to which the eNodeB 115 will do.
    [0037] In another embodiment, the relay node 110 is arranged to indicate directly to the eNodeB 115 that it is a relay node, for example by means of Radio Resource Control, RRC. In this mode, the relay node 110 is arranged to transmit one or more connection messages to the eNodeB, as one or more of: • a dedicated Radio Resource Control message; • a dedicated establishment cause in an RRC Connection Request message, • a dedicated indication in a complete RRC Connection Preparation message, • a random access preamble, where the random access information is suitable for use in the cell is transmitted through the base station serving the cell.
    [0038] As mentioned, the relay node 100 is arranged to receive, along with the unsupported indication, the additional information that was enumerated above.
    [0039] The relay node 110 is arranged to try to establish itself as a relay node in another cell upon receiving the no-support indication. In one embodiment, the relay node uses the additional information, which the relay node receives along with the no-support indication, when the relay node tries to establish itself as a relay node in another cell, upon receiving the indication of unsupported.
    [0040] In one embodiment, the relay node 110 stores the indication about the unsupported relay node and the additional information, in the embodiments in which the received additional information can be used for future cell reselection decisions. For example, cells that are associated with another relay node will most likely not be future supporting relay nodes either. On the other hand, an eNodeB that does not have relay node support software at some point in time may have been upgraded, and may be able to handle relay nodes in the future.
    [0041] In another embodiment, the relay node 110, knowing that the eNodeB 115 does not support relay nodes, is arranged to update status information in a local management system of the relay node or the site. Modified status information may include error codes or other indications such as lights, beeps, etc., which may be received by operator personnel. The error codes can provide information about why the relay node 110 cannot attach a relay to the current eNodeB 115.
    [0042] In one embodiment, the relay node 110 is arranged to receive the list of one or more cells that support relay nodes, herein also called "white list cells", and/or the list of one or more cells that do not support relay nodes, here also called "blacklist cells", in the form of one or more ranges of cell identifiers. Cell identifiers are, in one embodiment, the eight-bit cell identifier of the E-UTRAN Cell Identifier. This notion will be explained with reference to Fig.4, which shows the structure of an E-UTRAN Cell Identifier.
    [0043] In LTE, cells are locally identified by a sequence of signals from an enumerated set. In LTE there are 504 signal sequences, each associated with a Physical Cell Identity, PCI. Furthermore, a cell broadcasts in the E-UTRAN Cell Identifier, a 28-bit cell identifier that identifies a cell within a Public Land Mobile Network, PLMN.
    [0044] The cell identifiers used between the eNodeBs are specified, as well as the cell identifiers used between an eNodeB and a core network. The 28-bit cell identifier is divided into two parts: • an eNodeB ID identifying the eNodeB, • cell identifiers of the cells served by the eNodeB.
    [0045] In the case of the so-called eNodeB macro, the eNodeB ID comprises 20 bits, which leaves 8 bits to identify the cells, and in the case of the so-called eNodeB, the eNodeB ID 20 is identified by 28 bits, and can consequently understand only one cell. Figure 4 illustrates the relationship between Cell and eNodeB identifiers. It is thus in the cell identifiers that the relay node 110 is arranged to receive a cell list range as "white" or "black".
    [0046] As mentioned, the relay node is arranged to identify itself as a relay node in a cell 125 in the radio access network. This identification is suitably performed for a network node, either in the radio access network, or in the core network. Three main cases can be highlighted with regard to the network node: • the network node is a Mobility Management Entity, LTE MME. Here it is the MME that terminates the NAS (No Access Layer) signaling to the relay node, which has an interface S1 established with the eNodeB serving the relay node, • the network node is eNodeB 115 serving the relay node , • the network node is a special configuration node.
    [0047] These cases will be described in more detail below, since the invention also discloses a network node for a Radio Access Network or for a Core Network, which network node can, in various forms, be a of the three nodes listed above. However, in case the network node is an eNodeB 115, the unsupported indication that the relay node 110 is arranged to receive will be described in the following: in this case, the lack of a response from the eNodeB 115 to an indication of relaying from the relay node 110 is interpreted by the eNodeB 110 as an indication by the relay node that the relay nodes are not supported by the serving eNodeB 115, i.e., an indication of no support.
    [0048] In such an embodiment, the control unit 225 at relay node 110 starts a timer at a predetermined time during the establishment of the RRC connection, and if the timer expires before relay node 110 receives any signaling that it is only one eNodeB that supports the relay nodes sent, this is interpreted by the control unit 225 of the relay node 110 as an indication of no support.
    [0049] In an embodiment, in which the relay node 100 is arranged to transmit its own and more connection messages to a separate configuration node in the radio access network, or in a core network to which the access network over radio is connected, the relay node 100 is arranged to receive an indication of unsupported and additional information from the configuration node.
    [0050] The invention also discloses a network node for a Radio Access Network or a Core Network. A schematic block diagram of this network node is shown in Fig.4. As will be appreciated, the network node 400 comprises many of the generic components, such as those of the relay node 110. As shown in Fig. 4, the network node 400 comprises a receiving unit Rx 415 and a transmitting unit Tx 420 The transmitting unit 220 and the receiving unit 215 are intended to indicate the units which are adapted to transmit and receive, respectively, the messages in a wireless or wired manner, depending on the application. The transmitting unit 420 and the receiving unit 415 are connected to a communications interface 410, whereby they communicate with the other units, whether wireless or ground lines, as the case may be.
    [0051] The network node 400 also comprises a control unit 425 for controlling the function of the relay node, including the functions of the transmit and receive units 420, 415. In addition, the relay node 400 also comprises a unit of memory 430, connected with the control unit, for storing the data for the operation of the relay node 400.
    [0052] The network node 400 is arranged to receive one or more messages as part of an initial connection procedure from the User Equipment 110 in a first cell, like 125 of Fig. 1, of an Access By Network. radio.
    [0053] The network node 400 is arranged to use one or more messages to identify the User Equipment as relay node 1110, in the first cell 125, and is also arranged to, by identifying the User Equipment as a node of relay 110, transmits an indication of no support to the relay node 110 indicating that the base station 115 serving the first cell 125 does not support a relay node 110.
    [0054] In one embodiment, the network node 400 is also arranged to transmit to the relay node 110 the indication of why the base station 115 serving the first cell does not support a relay node 110.
    [0055] In one embodiment, the network node 400 is also arranged to transmit to the relay node 110 one or more unsupported indications, from the following: • an alternative carrier or frequency band intended for communications of the relay node; • an alternative Radio Access Technology intended for relay node communications; • a list of cells that support relay nodes; • a list of cells that do not support relay nodes.
    [0056] In one of this embodiment, the network node is arranged to transmit the list of cells and/or base stations as a dedicated set of cell identifiers, such as the cell identifier part of the E-URAN Cell Identifier , that is, the "white" or "black" cell lists mentioned above comprise a set of cell identifiers.
    [0057] In one embodiment, the network node 400 is an LTE Mobility Management Entity, and the initial connection procedure in which one or more messages from the UE are part of an Attachment Procedure.
    [0058] In an embodiment in which the network node 400 is an MME, the MME is equipped with a list of eNodeBs in the Radio Access Network 100, which supports, or does not support, the relay node 110, and the MME is based on the unsupported indication to the relay node 110 via the list, with the unsupported indication being a Reject Attach via NAS signaling.
    [0059] In an embodiment in which the network node 400 is an MME, the MME is arranged to signal a relay node indication to the eNodeB 115 about a specific UE served by the eNodeB 115, in this case the "UE" 110, and to receive a negative indication from the eNodeB 115, indicating that the eNodeB does not support the relay node function. In this mode, the MME 400 is arranged to then send a Reject Attachment to the relay node 110 via the eNodeB 115. The negative indication from the eNodeB 155 will suitably be an error protocol or a dedicated message. not supported by the relay node.
    [0060] The case in which the network node is an LTE MME is also schematically illustrated in Fig. 6: the relay node 110 performs the establishment of an RRC connection with the eNodeB 115, after which the relay node 100 transmits a NAS Attach Request with the MME 400. In one case, the MME already knows that the eNodeB 115 does not support relay nodes, in which case the MME can immediately respond with a NAS Attach Reject. Alternatively the establishment of the RRC Connection is followed by a NAS Attach Request, and an initial Context Preparation takes place between the eNodeB 115 and the MME 400, after which the MME 400 transmits the Reject NAS Attachment to the relay node 100 per through the eNodeB 115.
    [0061] In one embodiment, the network node 400 is an eNodeB of an LTE, such as 0 115 of Fig. 1, and is arranged to transmit the unsupported indication to the relay node 110, as one or more between: • a dedicated RRC message, • a proprietary message, • a dedicated release cause for the RRC Connection Release, • an RRC Connection Reject message.
    [0062] In one embodiment, the network node is a separate configuration node, either for the radio access network or for the core network, which is arranged to receive the one or more messages that are part of the initial connection procedure from the User Equipment 110 during the connection procedure to the configuration node in which the User Equipment 110 transmits information about itself to the configuration node. The information that the relay node transmits about itself to the configuring node comprises information such as the identity of the relay node, SIM details of the relay node; information of the eNodeB serving, such as E-UTRAN cell identifier, tracking area codes, PCI, relay node capabilities, software version, its estimated location information, relay node IMSI, IMEI, etc.
    [0063] In general, the modality in which the network node is a configuration node in the core network, the functions will be described in the following text. It should be noted that the case where the configuration node is placed in the radio access network works in a similar way.
    [0064] The relay node 110 establishes connectivity to the core network 120 through attach procedures. Relay node 100 discloses or obtains the address of configuration node 400, i.e., a core network node dedicated at least in part to providing relay nodes with the initial configuration information, and signals an indication to this configuration node , as part of the connection procedure for the configuration node, which connection procedure was described above, comprising the indication the information listed above.
    [0065] Configuration node 400 then indicates to relay node 110 whether or not eNodeB 115 supports relay nodes. If the eNodeB 115 does not support relay nodes, the configuration node 400 may provide a reselection information as described above, for example between: • an alternative carrier or frequency band intended for relay node communications; • an alternative Radio Access Technology intended for relay node communications, • a list of cells that support relay nodes, • a list of cells that do not support relay nodes.
    [0066] The configuration node can be configured based on neighbor cell relationship information, as well as relay node support capabilities of different cells and eNodeBs, and the configuration can be performed manually or automatically by the Domain Manager.
    [0067] In the procedure of the relay node to obtain connectivity with the core network, the MME may have disclosed that the eNodeB 115 does not have relay node support. If the configuration node, such as the one disclosed herein, is present, the MME instead signals "attachment accepted" to the relay node 110 to allow the relay node 110 to maintain connectivity to the network. In one embodiment, the MME also signals connectivity information such as, for example, an IP address of the configuration node, or information about the configuration node that can be used to derive the IP address of the configuration node.
    [0068] The signaling in the case where the network node is a separate configuration node is shown in Fig. 7: what is shown there is that the MME, although it already knows when the relay node attaches to the network, that eNodeB 115 does not support relay nodes. However, the MME still accepts the attach request from the relay node to allow the relay node to make contact with the configuration node.
    [0069] The invention also discloses a method for the operation of the relay node. A schematic flowchart of this method 800 is shown in Fig. 8, in which steps that are optional or alternative are shown in dotted lines.
    [0070] The method comprises the operation, step 805, of a relay node, in a radio access network, as a relay node between one or more User Equipment in a radio access network cell and a station base serving the cell.
    [0071] Method 800 further comprises, step 810, arranging the relay node to identify itself as a relay node in the cell in the radio access network (100), and also comprises receiving, step 815, at the node of a relay node, an indication of no support from the relay node, indicating that the base station serving the cell is unable to support a relay node, and upon receiving the no support indication at the relay node, leave the node The relay attempts to establish itself, step 816, as a relay node in another cell.
    [0072] In one embodiment, as indicated in step 820, method 800 further comprises transmitting from a relay node one or more connect messages as part of the initial connection procedure, to let the relay node identify the itself as a relay node in the cell, in the radio access network.
    [0073] In one embodiment, as indicated in step 825, the method comprises receiving, together with an unsupported indication of additional information comprising one or more of: - an indication of why the base station serving the cell is unable to support relay nodes, - an alternative carrier or frequency band intended for relay node communication; - an alternative Radio Access technology, RAT, intended for relay node communication, - a list of one or more cells where relay nodes are supported, - a list of one or more cells where relay nodes are not supported the relay nodes, and the use of this additional information in the relay node's attempt to establish itself as a relay node in another cell.
    [0074] The invention is not limited to the examples and embodiments described above and shown in the drawings, and may be modified freely within the scope of the appended claims. For example, as mentioned above, the invention can also be applied to systems such as WCDMA and GSM. In the case of WCDMA, the network node may be a Radio Network Controller, RNC, or an eNodeB, whereas in the case of GSM the network node may be a Base Station Controller, BSC, or a Base Transceiver Station , BTS. In both cases, that is, both in the case of WCDMA and in the case of GSM, the network node can either be a Mobile Switching Center, MSC, a Support Node Serving GPRS, SGSN, or a Support Node of Gateway GPRS, GGSN.
    权利要求:
    Claims (16)
    [0001]
    1. Relay node (110), to a radio access network (100), arranged to be a relay node (110) between one or more User Equipment (105) in a cell (125) of the access network and a base station (115) serving the cell, the relay node (110) being arranged to identify itself as a relay node (110) in the cell (125) in the radio access network (100), the relay node (110) being also arranged to receive a non-support indication indicating that the base station (115) serving the cell (125) is unable to support the relay node (110) and in which the relay node (110). relay (110) is arranged to, upon receipt of said unsupported indication, attempt to establish itself as a relay node (110) in another cell, the relay node (110) being characterized by the fact that it is willing to transmit said one or more connection messages to a separate configuration node in the network of radio access or in the core network to which the radio access network is connected and being arranged to receive said no-support indication from the separate configuration node and being willing to receive, together with the no-support indication , additional information comprising one or more of: an indication of why the base station (115) serving the cell (125) is unable to support relay nodes (110), an alternate carrier or frequency band intended for node communication a relay (110), an alternative Radio Access technology, RAT, intended for relay node communication (110), a list of one or more cells supported by relay nodes (110), a list of a or more cells in which relay nodes are not supported (110), the relay node (110) being arranged to use said additional information when trying to establish itself as a relay node (110) in another cell.
    [0002]
    2. Relay node (110) according to claim 1, characterized in that it is arranged to identify itself as a relay node (110) in the cell (125) by transmitting one or more messages connection as part of an initial connection procedure.
    [0003]
    3. Relay node (110), according to claim 2, characterized by the fact that it is arranged to interpret a lack of response to one or more connection messages as an indication of unsupported.
    [0004]
    4. Relay node (110), according to claim 3, characterized in that it is arranged to transmit the one or more connection messages as one or more of: a dedicated Radio Resource Control message, a cause of set up in an RRC Connection Setup Request message, a dedicated indication in an RRC Connection Setup Complete message, a random access preamble, where information about the random access preamble suitable for use in the cell is transmitted by the base station (115) serving the cell (125).
    [0005]
    5. Relay node (110), according to any one of claims 1 to 4, characterized in that it is arranged to receive the list of one or more cells that support relay nodes (110), and/or the list of one or more cells that do not support relay nodes (110), in the form of one or more cell identifier ranges.
    [0006]
    6. Network node for a Radio Access Network (100) or a Core Network, the network node being arranged to receive one or more messages as part of an initial connection procedure, from a User Equipment in a first cell (125) of the Radio Access Network, the network node being arranged to use said one or more messages to identify the User Equipment as a relay node (110) in said first cell (125) and in which the network node is arranged to, upon identification of the User Equipment as a relay node (110), transmit an indication of non-support to the relay node (110), indicating that the base station (115) serving the said first cell (125) does not support a relay node (110) the network node characterized in that it is also arranged to transmit to the relay node (110) one or more of: an alternative carrier or intended frequency band for node communications (110), an alternative Radio Access Technology intended for relay node communications (110), a list of cells that support relay nodes (110), a list of cells that do not support relay nodes (110) , an indication of why the base station (115) serving the first cell does not support a relay node (110).
    [0007]
    7. Network node according to claim 6, characterized in that it is arranged to transmit the list of cells and/or base stations as a dedicated set of cell identifiers, such as the cell identifier part of the E-UTRAN Cell Identifier.
    [0008]
    8. Network node, according to claim 7, characterized by the fact that it is an LTE Mobility Management Entity, in which the initial connection procedure is an Attachment Procedure.
    [0009]
    9. A network node, according to claim 8, characterized in that the Mobility Management Entity is equipped with a list of eNodeBs in the Radio Access Network (100) that supports or does not support a relay node ( 110), on which the Mobility Management Entity lists the non-support indication for the relay node (110), on which the mentioned indication is a Reject Attachment.
    [0010]
    10. Network node, according to claim 9, characterized in that the Mobility Management Entity is arranged to signal an indication from the relay node (110), to an eNodeB, about the specific User Equipment served by the eNodeB and to receive a negative indication from the eNodeB indicating that the eNodeB does not support a relay node (110), and the Mobility Management Entity is willing to then send a Reject Attachment to the relay node (110) per through the aforementioned eNodeB.
    [0011]
    11. A network node, according to claim 10, characterized in that in the Mobility Management Entity, the negative indication from the eNodeB is a protocol error or an unsupported message from the relay node (110 ) dedicated.
    [0012]
    12. Network node according to claim 6, characterized in that the LTE eNodeB is arranged to transmit said non-support indication to the relay node (110), said indication being one or more among : a dedicated RRC message, a proprietary message, a dedicated Release Cause to Release RRC Connection, an RRC Connection Reject message.
    [0013]
    13. Network node, according to claim 6, characterized in that it is a separate configuration node for each radio access network or Core network, which is arranged to receive the one or more messages that are part of a initial connection procedure from the User Equipment (110), during a connection procedure in which the User Equipment (110) transmits information about itself to the configuration node, said information including an identification that the Equipment User is a relay node (110).
    [0014]
    14. Network node, according to claim 13, characterized in that it is arranged to receive from the User Equipment (110) in the initial connection procedure, one or more of the following: tracking area information, the Base station ID (115) of the cell (125) of the relay node (110), the global cell identifier of the cell of the relay node (110), the estimated spatial position of the relay node (110), an identifier of relay node (110), a relay node IMSI, a relay node IMEI (110).
    [0015]
    15. Method (800) for operating (805) a relay node (110) in a radio access network (100) as a relay node (110) between one or more User Equipment (105) in a cell (125) of the radio access network (100) and a base station (115) serving the cell (125), comprising arranging the relay node (110) to identify itself (810) as a relay node (110 ) in the cell (125) in the radio access network (100), the method (800) also comprising receiving (815), at the relay node (110), an indication of no support, indicating that the base station (115 ) serving the cell (125) is unable to support a relay node (110), and upon receipt of the non-support indication at the relay node (110), let the relay node (110) try (816) to establish itself as a relay node (110) in another cell, the method (800) being characterized by the fact that it also comprises transmitting the aforementioned one or more messages connections to a separate configuration node in the radio access network (100) or in a core network to which the radio access network (100) is connected and being arranged to receive said unsupported indication from from the separate configuration node, and receive (820), along with said indication of unsupported, additional information comprising one or more of: an indication of why the base station (115) serving the cell (125) is unable of supporting relay nodes (110), an alternative carrier or frequency band intended for relay node communication (110), an alternative Radio Access Technology, RAT, intended for relay node communication (110), a list of one or more cells that relay nodes are supported (110), a list of one or more cells that relay nodes are not supported (110), and use this additional information in the relay node's attempt ( 110) of and establish itself as a relay node (110) in another cell.
    [0016]
    16. The method (800) according to claim 15, further comprising transmitting from the relay node (110) one or more connection messages (825) as part of an initial connection procedure, to let the relay node (110) identify itself as a relay node (110) in the cell (125) in the radio access network (100).
    类似技术:
    公开号 | 公开日 | 专利标题
    BR112012032065B1|2021-07-27|RELAY NODE TO A RADIO ACCESS NETWORK, NETWORK NODE TO A RADIO ACCESS NETWORK OR A CORE NETWORK AND METHOD FOR OPERATING A RELAY NODE IN A RADIO ACCESS NETWORK
    ES2705877T3|2019-03-26|Transfers instructed from the WLAN network to another radio access network
    ES2796123T3|2020-11-25|Detect and report a radio network problem that occurs in a second cell in a user equipment that has a radio resource connection established in a first cell
    US11051233B2|2021-06-29|Base station, radio terminal, and methods and non-transitory computer-readable media therefor
    ES2610634T3|2017-04-28|Method to provide information in a cellular wireless communication system
    EP3272178B1|2019-01-02|Communications network
    KR101411968B1|2014-06-26|Self-configuration of donor/relay node relationship
    US9055492B2|2015-06-09|Method and a network node for sharing information over an interface in a telecommunications system
    BR112012025070B1|2022-02-15|Operations and Maintenance Node and Related Method
    BR122016000399B1|2019-05-07|TERMINAL IN A MOBILE COMMUNICATION SYSTEM UNDERSTANDING AT LEAST ONE BASE STATION AND COMMUNICATION METHOD FOR THE TERMINAL
    US20170289855A1|2017-10-05|Method and apparatus for enhancing mobility for 3gpp lte-wlan aggregation in wireless communication system
    US9756670B2|2017-09-05|Method and system for notifying transport layer address
    BR112013004871B1|2022-01-18|TARGET BASE STATION FOR A COMMUNICATION NETWORK, METHOD FOR OPERATING A TARGET BASE STATION, METHOD FOR OPERATING A MOBILITY MANAGEMENT ENTITY AND MOBILE COMMUNICATION DEVICE
    ES2809471T3|2021-03-04|Method for better communication between network nodes of a mobile communication network, mobile communication network, program and computer program product
    BR112012003455A2|2020-03-10|METHOD FOR PAYING AN EMERGENCY USER AND SYSTEM FOR PAYING AN EMERGENCY SERVICE USER
    JP6547063B2|2019-07-17|Device-to-device communication method, device, and system
    BR112020002493A2|2020-08-04|base station and radiocommunication method
    US9185584B1|2015-11-10|Dual controller functionality in a wireless communication system
    EP2384050A1|2011-11-02|Transmission of the format of a cell identifier in a handover
    EP2975816A1|2016-01-20|Method and system for notifying transport layer address
    KR20180010381A|2018-01-31|Method and apparatus for handover between WLAN termination
    CN112262590A|2021-01-22|Cell global identity reporting
    WO2020202078A1|2020-10-08|Handling of emergency services for non-public networks
    US20150071162A1|2015-03-12|Method and apparatus for transmitting indication in wireless communication system
    同族专利:
    公开号 | 公开日
    IL223530A|2016-10-31|
    US9237491B2|2016-01-12|
    BR112012032065A2|2016-11-08|
    US20130090123A1|2013-04-11|
    EP2586268A1|2013-05-01|
    CN102960048B|2017-03-15|
    US20140364124A1|2014-12-11|
    WO2011162651A1|2011-12-29|
    US8811998B2|2014-08-19|
    EP2586268A4|2016-03-09|
    CN102960048A|2013-03-06|
    EP2586268B1|2016-11-16|
    引用文献:
    公开号 | 申请日 | 公开日 | 申请人 | 专利标题
    JP4073808B2|2003-03-17|2008-04-09|シャープ株式会社|Network restructuring method, node, network restructuring program, and computer-readable storage medium storing the program|
    US20070070929A1|2005-09-28|2007-03-29|Samsung Electronics Co., Ltd.|Apparatus and method for negotiating relay station capability in a multi-hop relay broadband wireless access communication system|
    CN101188816B|2006-11-15|2011-06-15|华为技术有限公司|Relay method, relay system and relay device|
    US20090310584A1|2008-06-13|2009-12-17|Fujitus Microelectronics Limited|Self Organizing Network|
    CN101299832B|2008-06-20|2012-06-27|华为技术有限公司|Method, system and equipment for interface data transmission between base station and controller|
    KR101430491B1|2008-10-10|2014-08-14|엘지전자 주식회사|Method for transmitting reference signals for relay node|
    KR101622406B1|2009-04-24|2016-05-19|엘지전자 주식회사|Apparatus and method of accessing network in wireless communication system|CN102348255B|2010-07-30|2016-07-06|中兴通讯股份有限公司|A kind of via node accesses the method and system of network|
    EP2652997A4|2010-12-17|2017-01-04|Nokia Solutions and Networks Oy|Dynamic configuration of relay nodes in a cellular communication system|
    US8811347B2|2011-06-16|2014-08-19|Lg Electronics Inc.|Method and apparatus for selecting MME in wireless communication system including mobile relay node|
    CN102833875B|2011-06-16|2016-05-25|华为技术有限公司|Via node method of network entry and relevant apparatus|
    GB2495145A|2011-09-30|2013-04-03|Nec Corp|Relay services used in LTE advanced systems|
    JP6207397B2|2011-11-04|2017-10-04|三菱電機株式会社|Mobile communication system|
    CN103220816B|2012-01-19|2018-05-15|北京三星通信技术研究有限公司|A kind of interface between RN and core net is established and communication means|
    WO2013127424A1|2012-02-27|2013-09-06|Telefonaktiebolaget Lm Ericsson |Method and apparatus in a network node for establishing neighbor cell relations in a wireless network|
    EP2925034B1|2012-11-22|2019-07-31|Huawei Technologies Co., Ltd.|Network element access method and device|
    CN107211297B|2014-11-07|2021-07-23|交互数字专利控股公司|Method for selecting relay node executed by remote wireless transmitting/receiving unit and wireless transmitting/receiving unit|
    WO2016163735A1|2015-04-08|2016-10-13|Lg Electronics Inc.|Method and apparatus for transmitting relay support indication in wireless communication system|
    US9930634B1|2015-06-11|2018-03-27|Sprint Spectrum L.P.|Systems and methods for efficient updating of tracking area information for relay based networks|
    US20170325270A1|2016-05-06|2017-11-09|Futurewei Technologies, Inc.|System and Method for Device Identification and Authentication|
    JP6470714B2|2016-08-08|2019-02-13|ソフトバンク株式会社|Relay device and mobile communication system|
    US11160134B2|2017-08-09|2021-10-26|Lg Electronics Inc.|Method for performing RRC connection procedure in wireless communication system and apparatus therefor|
    WO2019232683A1|2018-06-04|2019-12-12|华为技术有限公司|Cell establishment method and device|
    法律状态:
    2019-01-15| B06F| Objections, documents and/or translations needed after an examination request according [chapter 6.6 patent gazette]|
    2020-01-28| B06U| Preliminary requirement: requests with searches performed by other patent offices: procedure suspended [chapter 6.21 patent gazette]|
    2021-07-06| B09A| Decision: intention to grant [chapter 9.1 patent gazette]|
    2021-07-27| B16A| Patent or certificate of addition of invention granted|Free format text: PRAZO DE VALIDADE: 20 (VINTE) ANOS CONTADOS A PARTIR DE 22/06/2010, OBSERVADAS AS CONDICOES LEGAIS. PATENTE CONCEDIDA CONFORME ADI 5.529/DF, QUE DETERMINA A ALTERACAO DO PRAZO DE CONCESSAO. |
    优先权:
    申请号 | 申请日 | 专利标题
    PCT/SE2010/050711|WO2011162651A1|2010-06-22|2010-06-22|Method and device for a relay node|
    [返回顶部]